Information handling system controller scalable interface

ABSTRACT

A portable information handling system interacts with a game controller through either a direct connection at a wired interface at the sides of opposing controller housings and the information handling system housing or through a bridge having a bridge housing that directly couples to the controller housing as a bridge to the information handling system, such as with a wireless interface. During a sliding coupling motion, pins of the controller housing wired interface move across pins of the bridge or information handling system wired interface. Analysis of the interface signals through a sliding coupling motion identifies the type of controller housing, such as a controller housing with game input devices or with extra functions like speaker audio and supplemental battery power.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/731,426, filed Dec. 31, 2019, entitled “Information Handling SystemController Scalable Interface,” naming Gerald R. Pelissier, Yagiz C.Yildiz, Kevin M. Turchin, Shu-Wei Chou, and Tsung Wen Hsueh asinventors, which application is incorporated herein by reference in itsentirety.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to the field of informationhandling system communication interfaces, and more particularly to aninformation handling system controller scalable interface.

Description of the Related Art

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Information handling systems are commonly used as gaming platforms thatrun gaming applications. Typical gaming applications rely upon theavailability of substantial processing capability to provide an end userwith an acceptable gaming experience. Heavy processing tasks include notjust interacting with the end user through one or more input devices,but interacting with multiple external players through networkcommunications. In addition, gaming applications typically lean heavilyon graphics processing capabilities to quickly and accurately present agame user interface with high resolution. Intense information andgraphics processing tends to have a heavy power draw and to create highlevels of thermal energy dissipated by the central processing unit andgraphics processing unit. Often gamers purchase high end desktop systemswith premium processing, graphics and thermal capabilities. Generally,non-portable desktop systems offer the best form factor for includingthe capabilities that gamers seek.

Some gamers who travel will also use portable information handlingsystems to play gaming applications. Portable information handlingsystems designed to support gaming applications tend to have larger andheavier housings that will support greater processing, graphics andthermal demands. A typical portable information handling system designedto meet gaming demands will include a 17 inch flat panel display in aclamshell housing and a graphics processing unit that will support highresolution images at peripheral display. Smaller housing sizes willsupport gaming applications but tend to lose processing and thermalcapabilities as housing size shrinks. Generally, end users of portableinformation handling systems will have a cradle or docking station athome that leverages the processing capabilities of the system withexternal peripheral devices, such as a keyboard, mouse, and gamecontroller with a joystick, trigger and other button input devices.

One difficulty with using a portable information handling system to playgames in a mobile situation is that the input devices integrated in aportable information handling system tend to have limited capabilitiesfor gaming applications. An end user may use an integrated keyboard andmousepad to perform inputs, however, these input devices are tied to thedisplay by the clamshell housing so that consuming visual images is moredifficult. An alternative is to carry separate peripheral input devicesto use while playing games, such as a wireless or USB game controller.Often, these additional devices are inconvenient to carry and to trackwhile mobile. An end user tends to spend a good deal of time setting uphis system to play so that a quick access while between flights is tootime constrained.

Some gamers use mobile systems dedicated to gaming for mobile play, suchas the NINTENDO SWITCH. These specialized mobile systems integrategaming controllers in the same housing as a display so the end userholds the housing with the display in a viewing position while makinginputs at a joystick, trigger and buttons integrated in the housing.Such specialized systems tend to have limited capabilities and lock theuser into integrated inputs devices. The display tends to have limitedresolution and the system does not typically support other informationhandling system tasks like word processing, email and web browsing.Thus, the end user generally has to take the specialized gaming systemin addition to an information handling system for regular processingtasks. Further, specialized gaming systems with integrated input devicestend to take a good deal of damage during normal use as end users tendto get excited while playing games. These normal gaming input forces candestroy input devices in short order if the specialized gaming systemdoes not have a robust design. Further, where end users tend to engagein extended gaming sessions, these smaller specialized systems canbecome uncomfortable over time.

SUMMARY OF THE INVENTION

Therefore, a need has arisen for a system and method which provides aninformation handling system with a detachable game controller.

In accordance with the present invention, a system and method areprovided which substantially reduce the disadvantages and problemsassociated with previous methods and systems for performing inputs at aninformation handling system. An information handling system having atablet form factor in a planar housing executes a gaming application topresent a gaming user interface at an integrated display. First andsecond game controllers to accept inputs to the gaming applicationselectively attach and detach at opposing sides of the informationhandling system. When attached to the information handling system, thegame controllers communicate inputs through a wired interface directlyto the information handling system, such as joystick, button and triggerinputs. When detached from the information handling system, the gamecontrollers attach to opposing sides of a bridge to communicateindirectly with the information handling system intermediated by thebridge, such as through wireless or cabled interface between the bridgeand information handling system.

More specifically, a portable information handling system processesinformation with a central processing unit (CPU) and memory disposed ina planar housing and presents the information as visual images at anintegrated display through a graphics processing unit (GPU). Anattachment structure at each of opposing sides of the planar housingdetachably engages with first and second game controllers that includeinput devices to accept inputs from an end user, such as a joystick,input buttons and a trigger. A wired interface disposed in theattachment structure, such as pogo pins aligned with contact pads,directly communicate inputs at the input devices to the informationhandling system, such as for inputs to a gaming application. In thishandheld configuration, an end user grasps the game controllers atopposing sides of the planar tablet to perform inputs at the inputdevices while viewing the display. The handheld configuration couplesthe game controllers in the plane of the planar housing to provide acomfortable gaming position and ready mobility. The game controllersdetach from the planar housing so that the information handling systemconverts to a tablet configuration and, with a stand integrated in therear side, rests on a support surface to operate in a standaloneconfiguration. The game controllers attach to a bridge structure havingthe attachment structure to define a wired interface between the bridgeand a game controller on each of opposing sides of the bridge. Inputs atthe game controller are communicated to the bridge through the wiredinterface, such as through an I2C interface, and then from the bridge tothe information handling system through a wireless, USB and/or IPinterface. In the standalone configuration, the game controllers incooperation with the bridge provide a peripheral game controller forinputs to the information handling system.

The present invention provides a number of important technicaladvantages. One example of an important technical advantage is that anend user is provided with increased flexibility for interacting with aninformation handling system. An end user can input to an informationhandling system in a handheld mode of operation by attaching gamecontrollers directly to the information handling system housing or in astandalone mode by attaching the game controllers to a separate bridge.Each of the game controllers, bridge and information handling systeminclude a processor, such as microcontroller unit (MCU) that coordinatescommunication, detects inputs and applies haptic and illuminationfeedback. These processor interactions provide additional flexibilityfor different game controllers to adapt optional features, such asspeakers or extra battery storage. The game controllers include robustinput devices, such as a trigger that rotates about an axis normal tothe plane of the housing to withstand high end user forces. By includinga powerful graphics processor unit in the information handling system,such as the INTEL Ice Lake and Tiger Lake system on chips withintegrated graphics processing, the standalone mode supports excellentgraphics presentation at both the integrated display and a peripheraldisplay. Portability for go-anywhere gaming is balanced with comfort andperformance to support extended gaming sessions with high performance.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference number throughout the several figures designates a like orsimilar element.

FIGS. 1A, 1B, 1C and 1D depict a portable information handling systemconfigured with detachable game controllers in handheld and peripheralconfigurations;

FIGS. 2A and 2B depict a side perspective view of the game controllerand bridge to illustrate an example embodiment of an attachmentstructure to couple the game controllers to an information handlingsystem and bridge;

FIGS. 3A, 3B and 3C depict a side perspective view of an alternativeembodiment of an attachment structure that couples a game controller 12to a bridge or information handling system;

FIG. 4 depicts a side perspective view of an alternative embodiment ofan attachment structure that couples a game controller to a bridge orinformation handling system;

FIG. 5 depicts a side perspective view of an alternative embodiment ofan attachment structure that couples a game controller to a bridge orinformation handling system;

FIG. 6 depicts a flow diagram of a process for tracking game controllersto accept inputs at an information handling system as game controllersattach and detach at an information handling system and bridge;

FIG. 7 depicts a flow diagram of a process for managing deactivation ofgame controllers at detachment from a bridge;

FIG. 8 depicts a logical block diagram of a storage structure fortracking game controllers at an information handling system and bridge;

FIG. 9 depicts a circuit block diagram of an example embodiment of aninformation handling system attached at opposing sides of a housing tofirst and second game controllers for direct communication through awired interface;

FIG. 10 depicts a circuit block diagram of an example embodiment of abridge attached at opposing sides of a housing to first and second gamecontrollers for supporting indirect communication of the gamecontrollers with an information handling system;

FIGS. 11A, 11B and 11C depict a flow diagram of an example embodiment ofidentification by a bridge or information handling system of gamecontroller type based upon wired interface contacts during a slidingattachment motion;

FIG. 12 depicts a flow diagram of a process for detecting gamecontroller active pin count during a sliding attachment motion;

FIG. 13 depicts an alternative embodiment of game controller pinarrangements having an identifier pin used as an indication of thenumber of used and empty wired interface pins;

FIGS. 14A and 14B depict a circuit block diagram of a seven pin countwired interface between an information handling system 10 and first andsecond game controllers 12 coupled at opposing sides;

FIGS. 15A and 15B depict a circuit block diagram of a six pin countwired interface between an information handling system and first andsecond game controllers having an identification pin repurposed tocontrol power;

FIG. 16 depicts a circuit block diagram of an example embodiment havingopposing pins pulled high and to ground to confirm attachmentconnections before game controller power up;

FIG. 17 depicts a flow diagram of a process for confirming gamecontroller attachment with the example embodiment of FIG. 16;

FIG. 18 depicts a flow diagram of a process for updating firmware atgame controllers, bridges, and information handling systems;

FIG. 19 depicts a flow diagram of a method for adapting haptic responseat a game controller based upon the type of operational configuration ofthe game controller;

FIG. 20 depicts a flow diagram of a process of adjusting haptic responsebased upon an orientation of a game controller;

FIG. 21 depicts an exploded view of a game controller having a verticalaxis trigger assembly to accept end user trigger inputs;

FIG. 22 depicts an exploded view of game controller covers aligned toassemble to a frame;

FIG. 23 depicts an exploded view of a trigger subassembly that couplesto a game controller frame;

FIG. 24 depicts a lower perspective view of a trigger actuation at amidframe;

FIG. 25 depicts a lower view of the trigger actuation at the midframe;

FIG. 26 depicts a lower front perspective view of a midframe toillustrate guide structures disposed to aid in trigger motion;

FIGS. 27A and 27B depict a lower perspective exploded view of anillumination assembly that provides illumination at a joystick extendingfrom an upper surface of a game controller;

FIG. 28 depicts an upper perspective view of a controller housingconical light guide portion;

FIG. 29 depicts a side perspective view of a flexible printed circuithaving LEDs to illuminate a joystick;

FIGS. 30A, 30B and 30C depict a joystick illuminated by five LEDsmounted at a bottom location; and

FIGS. 31A, 31B and 31C depict a joystick illuminated by ten LEDs mountedat a side location.

DETAILED DESCRIPTION

A portable information handling system adapts to handheld and stationarygaming input interactions with detachable gaming controllers thatselectively couple to opposing sides of the portable informationhandling system housing or to a bridge that provides communication as aperipheral input device. For purposes of this disclosure, an informationhandling system may include any instrumentality or aggregate ofinstrumentalities operable to compute, classify, process, transmit,receive, retrieve, originate, switch, store, display, manifest, detect,record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer, a network storage device, or any other suitable device and mayvary in size, shape, performance, functionality, and price. Theinformation handling system may include random access memory (RAM), oneor more processing resources such as a central processing unit (CPU) orhardware or software control logic, ROM, and/or other types ofnonvolatile memory. Additional components of the information handlingsystem may include one or more disk drives, one or more network portsfor communicating with external devices as well as various input andoutput (I/O) devices, such as a keyboard, a mouse, and a video display.The information handling system may also include one or more busesoperable to transmit communications between the various hardwarecomponents.

Referring now to FIGS. 1A, 1B, 1C and 1D, a portable informationhandling system 10 is depicted configured with detachable gamecontrollers 12 in handheld and peripheral configurations. FIG. 1Adepicts information handling system 10 in a handheld configurationhaving a first game controller 12 detachably coupled to a left sidesurface and a second game controller 12 detachably coupled to a rightside surface. Each game controller 12 includes a joystick 14 extendingout from an upper surface, input buttons 16 disposed at the uppersurface and one or more triggers 18 at a top side surface aligned forfinger placement in the grasp of an end user. Portable informationhandling system 10 has a tablet configuration with a display integratedat the upper surface to present information as visual images. In thehandheld configuration of the example embodiment, game controllers 12couple in a robust manner at the opposing sides of portable informationhandling system 10 to support an end user grasp so that input devices ofeach game controller 12, such as joystick 14, buttons 16 and trigger 18,are conveniently exposed to accept end user inputs while the end usergrasps each game controller 12. For instance, an end user playing agaming application on portable information handling system 10 has gamecontrollers 12 available and makes inputs to the game while holdingportable information handling system 10.

FIG. 1B depicts game controllers 12 detached from portable informationhandling system 10 in preparation of operation as a peripheral inputdevice. In the example embodiment, game controllers 12 couple to abridge 20 in the same manner as the couple to portable informationhandling system 10 so that bridge 20 acts as an intermediary tocommunicate game controller inputs to portable information handlingsystem 10. For example, as is described in greater detail below, gamecontrollers 12 engage with a sliding motion to bridge 20 to alignopposing wired interfaces between each game controller to a wiredinterface on each opposing side of bridge 20. Attachment structures ofgame controllers 12, bridge 20 and portable information handling system10 each include the opposing wired interfaces so that game controllers12 interchangeably interface with bridges and information handlingsystems to provide inputs to the information handling system gamingapplication. When game controllers 12 couple to an information handlingsystem, inputs from the input devices are communicated directly to theinformation handling system through the wired interface, such as an I2Cinterface. When game controllers 12 couple to a bridge 20, inputs fromthe input devices are communicated indirectly to information handlingsystem 10 first through the wired interface to bridge 20 and then frombridge 20 to information handling system through a separate interface,such as a wireless personal area network (WPAN) like Bluetooth, or acabled interface like a Universal Serial Bus (USB) cable and hub.

FIG. 1C depicts first and second game controllers 12 detachably coupledat opposing sides of a bridge 20 to build a composite game controllerthat interacts as a peripheral with portable information handling system10, such as by communicating game controller inputs to informationhandling system 10 through wireless signals. In the example embodiment,portable information handling system 10 has a stand 22 that extends outfrom the rear of its housing to hold portable information handlingsystem 10 in an elevated viewing position. Stand 22 rotates about ahinge in the bottom portion of information handling system 10 to openfrom the top out, thus reducing space used by stand 22. In thisstand-alone mode of operation, portable information handling system 10presents information as visual images based upon inputs from thecomposite controller assembly 28 through the wireless interface.Portable information handling system 10 is not restricted to executinggaming applications and may perform other processing tasks withinteractions from other input devices, such as a keyboard and mouse. Inaddition, portable information handling system 10 may supportpresentation of information as visual images at peripheral displays 26,such as through a display cable interface 24. During gaming operations,a variety of interactions may be provided when a peripheral display 26is available, such as using the integrated display to presentconfiguration or other information while providing the game userinterface at peripheral display 26. Similarly, if a peripheral display26 is interfaced while game controllers 12 couple directly to portableinformation handling system 10, the end user may present the gamingapplication user interface at peripheral display 26 while operating gamecontrollers 12 in the handheld mode depicted by FIG. 1A and presentingconfiguration or other supporting information at the integrated displayof portable information handling system 10. In the example embodiment,portable information handling system 10 is built into a housing having atrapezoidal shape of parallel top and bottom sides with the top side ofa shorter length than the bottom side. The trapezoidal shape aids systemstability in a stand-alone resting mode and provides a physicalindication to an end user of the housing orientation, such as to aidattachment of game controllers 12 in low light conditions in anergometric manner readily understood by an end user.

FIG. 1D depicts an exploded view of portable information handling system10 with example processing components that cooperate to processinformation. Generally, portable information handling system 10 has atablet configuration that executes instructions to present informationas visual images at an integrated display. For example, a planar housing30 holds a motherboard 32 that interfaces plural processing componentsthat cooperate to process information. In the example embodiment,motherboard 32 interfaces a central processing unit (CPU) 34 thatexecutes instructions to process information with a random access memory(RAM) 36 that stores the instructions and information. A solid statedrive (SSD) 38 or other persistent storage device stores instructionsduring power down states that are retrieved to RAM 36 at power up. Forexample, an operating system, such as WINDOWS, stored in SSD 38 isretrieved to RAM 36 to manage interactions with physical devices byapplications stored in SSD 38, such as gaming applications executable byCPU 34. A chipset 40 interfaces with CPU 34 to manage physicaloperations of CPU 34, such as clock speed, graphics interactions andmemory accesses. A graphics processing unit (GPU) 42 interfaces with CPU34 to accept visual information generated by the operating system andapplication for further processing that defines pixel values forpresentation of a visual image at integrated display 48 and peripheraldisplay 26. A wireless network interface card (WNIC) 44 interfaces withCPU 34 to provide wireless communication, such as through WiFi,Bluetooth and other wireless interfaces. A USB hub 46 supports cableinterfaces through a USB protocol, such as to communicate input deviceand graphics information with external devices. A display 48, such as aliquid crystal display (LCD) or organic light emitting diode (OLED)display, is disposed over the processing components and interfaced withGPU 42 to present information as visual images. The example embodimentdepicts only some of the various processing components that might beused in portable information handling system 10, and variousconfigurations of processing components may be selected in alternativeembodiments to achieve desired performance goals.

In one example embodiment, planar housing 30 may have a relatively thickconstruction as compared with conventional tablet information handlingsystems to provide a robust system that withstands exertions common ingaming application input devices. For instance, the Z-axis or thicknessrelative to the plane of planar housing 30 may provide additional spaceto include active cooling devices, such as a cooling fan for rejectingthermal energy created by power dissipation at CPU 34 and GPU 42. Activethermal rejection increases the capabilities of the CPU and GPUs thatmay be selected for processing information. In particular, a power GPU42 provides enhanced visual processing that supports a positive end userexperience in a gaming environment. In various embodiments, planarhousing 30 may have varied dimensions that offer a balance betweenhandheld and stationary usage cases and ergonomics versus portability.

Generally, portable information handling system 10, game controllers 12and bridge 20 cooperate to provide a flexible solution for a highquality gaming experience with optimal processing capabilities. Thecomposite controller assembly 28 is implemented with a three-pieceassembly having two game controllers 12 that unite to a bridge 20 tobecome a single functional composite game controller operative as aperipheral input device. Game controllers 12 detachably couple to eitherbridge 20 or information handling system 10 with an interchangeableattachment structure that readily converts the system between handheldand stationary operating modes. In the stationary use case, compositecontroller assembly 28 interfaces as a separate peripheral withinformation handling system 10 through wired and/or wirelessconnectivity while information handling system 10 acts as a stationary“head” device held in a viewing position by stand 22. Compositecontroller assembly 28 provides a slim ergonomically-performantcontroller unit that can support inputs to other types of informationhandling systems. When assembled to information handling system 10, gamecontrollers 12 convert information handling system 10 into a robusthandheld gaming unit with convenient grips and end user input devicesdisposed in proximity to the end user's grasp.

As an example of a usage scenario, an end user powers up informationhandling system 10 in the handheld configuration depicted by FIG. 1A.The end user end user, using a launcher such as Valve's Steam in BigPicture mode, initiates a game (gaming application). The gamingapplication presents the gaming user interface at integrated display 48.The handheld mode allows the user to play the game while mobile, thusgiving the user the flexibility of playing while walking around his homeor while traveling. Once the end user reaches a location to play in astand alone mode, the end user removes game controllers 12 from opposingsides of information handling system 10, such as with a slidingdetachment, places information handling system 10 on a support surface,such as elevated by stand 22, and attaches game controllers 12 to bridge20 to assemble a composite controller assembly 28. The end user may thencontinue the game application with inputs made from game controllers 12through bridge 20 to information handling system 10.

Referring now to FIGS. 2A and 2B, a side perspective view of gamecontroller 12 and bridge 20 illustrate an example embodiment of anattachment structure 50 to couple game controllers 12 to informationhandling system 10 and bridge 20. Attachment structure 50 provides arobust mechanical interconnect between game controller 12 andinformation handling system 10 and bridge 20 that withstands forcescommonly associated with gaming devices with ready detachment andattachment as desired by an end user. Solid coupling by attachmentstructure 50 prevents rattle and/or wobble between proximate housingthat can disrupt wired communication signals passing through wiredinterfaces disposed within attachment structure 50. Features ofattachment structure aid proper alignment during coupling and discourageattempts to couple misaligned housings or reverse install a right/lefthanded game controller on an opposite side of an information handlingsystem 10 or bridge 20. When game controllers 12 attach to a bridge 20or information handling system 10, a clean appearance is providedwithout gaps, holes or raw exposed mechanical features. These advantagesare provided with a number of different attachment structures asdescribed in greater detail below.

The example embodiment of FIGS. 2A and 2B has a magnetically guidedshort-throw “backbone” style rail coupling to mechanically couple gamecontroller 12 to bridge 20. At game controller 12, attachment structure50 has opposing lips 54 that define a rail with plural opposing slots52. Within a cavity defined by the opposing lips, a pogo pin connector56 exposes plural pogo pins that provide a wired interface to processingcomponents disposed within game controller 12. At the opposing length ofthe cavity from pogo pin connector 56, a latch 58 is disposed with anactuation button 60 exposed at the bottom outer surface of gamecontroller 12 and ramp feature 62 formed in the cavity leading towardslatch 58. Attachment structure 50 of bridge 20 has opposing plural tabs64 and a connector pad 66 disposed in a cavity defined between theopposing tabs 64. In one example embodiment, an anti-wear strip, suchas. Teflon, is located at the bottom of the slot to reduce wear fromsliding and tighten the fit of attachment structure 50. Tabs 64 aresized to fit within slots 52 and then slide under behind lips 54. Alatch connector 68 disposed in the cavity defined by opposing tabs 64couples to latch 58 as attachment structure 50 slides to an engagedposition having pogo pin connector 56 aligned with connector pad 66.Ramp feature 62 aids in a tight connection of attachment structure 50 bypressing tabs 64 out and against the back side of lips 54 as slidingengage of attachment structure 50 completes with latch 58 coupling tolatch connector 68 and aids with ejection of game controller 12 byfacilitating a sliding ejection motion at latch release activation. Inan alternative embodiment, attachment structure 50 may be reversed sothat tabs 64 are disposed on game controller 12 and slots 52 aredisposed on bridge 20.

To help ensure proper alignment of attachment structure 50, one or moremagnets 69 are embedded in each of opposing sides of attachmentstructure 50 to attract for proper sliding alignment and/or repel if animproper alignment is attempted. Magnetic polarity of embedded magnets69 is configured to selectively repel and/or attract attachmentstructure 50 when misalignment or proper alignment is attempted. Forinstance, an embedded magnet 69 located in a slot 54 is configured tohave a polarity opposite that of a magnet located at a tab 64 thataligns with it so that game controller 12 biases into the correctalignment during attachment. A second magnet at a proximate slot 54 hasan opposite polarity to the first magnet so that an attempt to couplegame controller 12 with the tab 64 having the same polarity will repelthe game controller 12 away from bridge 20. A second magnet may also beincluded in bridge 20 with an opposite polarity of the second magnet ofgame controller 12 so that the attraction and repel interactions arereinforced along the length of attachment structure 50. In oneembodiment, polarity configurations are arranged at left and right sidegame controllers 12 and bridge 20 so that an attempt to couple a leftside game controller to a right side of bridge 20 will provide arepelling force.

One advantage of attachment structure 50 in the example embodiment isthat the short-throw arrangement of slots 52 and tabs 64 allow a slidingmotion to attach game controller 12 to bridge 20 that involves only aportion of the length of attachment structure 50. This smaller slidingmotion helps to prevent exposure of attachment structure 50 visuallyafter attachment is complete to avoid compromise of the appearance ofcomposite controller assembly 28. In the example embodiment, at thestart of the sliding attachment motion, pogo pin connector 56 completelymisaligns with connector pad 66 at initial alignment of the correct slot54 and tab 64 so that pogo pin connector 56 runs across connector pads66 during a sliding coupling motion resulting in the individual pogopins of pogo pin connector 56 to contact the individual pads ofconnector pad 66 in a predictable pattern during attachment. As describebelow, this pattern of contacts provides an indication to a processor inbridge 20 of the type of controller housing that is being attached. Forinstance, some controller housings may include additional peripheralfunctions that the contact pattern helps to discern before attachment iscomplete. For instance, game controller 12 may include speakers toenhance sounds or a battery to provide additional battery life to aninformation handling system. In the example embodiment, attachmentstructure 50 is depicted at a bridge 20, however, information handlingsystem 10 includes a substantially identical attachment structure hasbridge 20 so that game controller 12 interchangeably couples to bridgesand information handling systems with a small sliding attachment anddetachment motion. In one alternative embodiment, the attachmentstructure 50 may be reversed so that the opposing lips 52 are integratedin bridge 20 and information handling system 10 with the tabs 64integrated in game controller 12.

Referring now to FIGS. 3A, 3B and 3C, a side perspective view depicts analternative embodiment of an attachment structure 50 that couples a gamecontroller 12 to a bridge 20 or information handling system 10. In theexample embodiment, attachment structure 50 has a dual guide feature 72disposed at the side surface of game controller 12 that fit into dualguides 70 formed in bridge 20 and information handling system 10. Dualguide feature 70 provides a gross to fine alignment with a narrow regionof each feature 72 fitting into an enlarged region of each guide 70 thatthen slides so that the narrow region of each guide feature 72 engagesunder the narrow region of each guide 70. In the example embodiment,only one of the guide features 72 bottom out on sliding engagement withthe guide 70 so that predictable alignment is achieved. Upon a completedsliding motion, latch 58 extends to engage in latch opening 68 with aplug 76 wired interface contacting a socket 74 wired interface. FIG. 3Cillustrates an example embodiment of latch 58 that biases upwards andout of game controller 12 under the influence of a biasing device 78,such as a spring. A press at latch button 60 overcomes the biasing forceso that latch 58 levers against game controller 12 to withdraw fromlatch opening 68. Attachment structure may be constructed from aluminumor a hard plastic to resist wear and lubricated with a Teflon materialto reduce friction during the sliding motion.

Referring now to FIG. 4, a side perspective view depicts an alternativeembodiment of an attachment structure that couples a game controller toa bridge or information handling system. The example embodiment providesa pair of opposing rails 80 with a double angled structure in whichalignment is facilitated with an initially loose fit at an attachingmember that slides down the rails towards a tighter fit when a latchlocks game controller 12 in position. The long throw rail approachreduces a risk of misalignment, however, the longer sliding motion isless convenient for an end user.

Referring now to FIG. 5, a side perspective view depicts an alternativeembodiment of an attachment structure that couples a game controller toa bridge or information handling system. Plugs extending from gamecontroller 12 fit into openings of bridge 20 and slide to engage. Asliding connector 84 engages with a fixed connector of the bridge andslides relative to game controller 12 to remain interfaced with thebridge connector during the sliding motion. By sliding connector 84during the coupling of game controller 12, wear effects on theelectrical connector is reduced over time since the pins remain engagedthrough the sliding motion of attachment.

Referring now to FIG. 6, a flow diagram depicts a process for trackinggame controllers to accept inputs at an information handling system asgame controllers attach and detach at an information handling system andbridge. In such a situation, the end user might experience delaysrelated to pairing of the bridge before inputs from the game controllerare provided to the gaming application and prioritization of differentpotential gaming inputs could become random or game specific behaviorAlthough detachable game controllers 12 provide improved end userflexibility for selection of an input configuration to interact with agame executing on an information handling system, in a gamingenvironment plural game controllers and bridges may be available toinput to an information handling system, which can result in confusionregarding which inputs should be used. For example, an end user mightdetach a game controller from an information handling system and couplethe controller to any of plural nearby bridges to interact wirelesslywith a gaming application. In such a situation, the end user wouldexperience delays related to pairing of the bridge before inputs fromthe game controller are provided to the gaming application andprioritization of different potential gaming inputs would be random orgame specific behavior. Further, where game controllers 12 havedifferent configurations of hardware, such as integrated speakers andalternative input devices, attachment to a bridge would involveadditional delays as hardware specific configuration information isexchanged between the bridge and information handling system. In atypical gaming environment, these configuration steps can potentiallyface additional confusion where multiple wireless devices are availableduring pairing discovery. In one example embodiment, a safety featuredisables functionality for unknown game controller identifiers to helpmanage unexpected or third party controllers that are detected.

FIG. 6 depicts logic that tracks game controllers that make inputs to aninformation handling system to manage different configurations thatinclude a direct coupling of a game controller to the informationhandling system or indirect communication of the game controller withthe information handling system through a bridge. One technique thataids in correct association of an end user with a game controller is totrack end user association based upon a game controller uniqueidentifier for each game controller associated with end user inputs. Forinstance, during a physical coupling with an information handlingsystem, the unique identifier of the game controller is retrieved to theinformation handling system and stored with a wireless pairing profile.Similarly, during a wireless or USB coupling of a game controller withan information handling system through a bridge, the game controllerunique identifier is retrieved to the information handling system andstored to aid tracking of the composite controller assembly thatincludes the game controller. Once pairing information is stored at theinformation handling system, wireless connectivity with a gamecontroller is provided by including the game controller uniqueidentifier in bridge pairing and advertising packets. During are-configuration of a game controller between direct communication andindirect communication through a bridge, “activate” and “deactivate”states are included with conventional wireless connection state machinesso that rapid and seamless game controller and bridge swapping aresupported. In addition, composite controller assembly descriptors aredefined that include each combination of identifiers associated witheach game controller, such as where multiple game controllers areswapped in various combinations with multiple bridges to interface withan information handling system. In this manner, swapping between gamecontroller input devices is managed through identification of the gamecontroller unique identifier and component composition with transitionsbetween configurations simplified through a deactivate state.

The process starts at step 86 with a start “not connected” stateexecuting at a bridge processor. At step 88, a game controller isattached to the bridge, such as with the attachment structure describedabove that interfaces the bridge and game controller wired interfaces.At step 90, the bridge firmware determines if the bridge has paired witha “head” information handling system. If not, the process continues tostep 92 to leave the configuration process flow and perform an initialpairing with an information handling system. In one example embodiment,advertising and pairing are automatically initiated in response toassembly of a game controller to the bridge. If the bridge is alreadypaired, the process continues to step 94 to transition to an activatingstate and initiate an activating timer. The activating state proceeds tostep 96 to determine if the bridge has both game controllers coupled as“wings” and, if so, ends with a connected state at step 102. If thebridge does not have both controllers connected, the activating statecontinues to step 98 to increment down the timer and then to step 100 todetermine if the timer has expired at a count of zero. If the timer hasnot expired, the process returns to step 96 to continue the activatingstate. If the timer expires at step 100, the process returns to step 86to restart when another game controller is coupled to the bridge.

Once the bridge firmware has transitioned to the connect state at step102, the process continues to step 104 to retrieve the unique identifierfrom each game controller wing coupled to the bridge. Once the gamecontroller unique identifiers are retrieved, the firmware proceeds tostep 106 to create a composite descriptor of the controller assemblybased upon both game controller wing unique identifiers. At step 108,the composite descriptor and the game controller unique identifiers areprovided to the information handling system, which defines the compositecontroller as the “primary” device for the game controller type and setsother connected composite game controllers as secondary. In addition, atstep 104 the process continues to step 110 to determine from the uniqueidentifiers whether any of the game controllers were previously attachedto the bridge as part of an existing composite device or as a directlyconnected device. If so, the process continues to step 112 to set thepreviously connected device to a “not connected” state. Once the uniqueidentifiers are associated with the composite assembly at step 108 andstep 112, the game controller database is updated at step 114 and theprocess ends at step 116.

Referring now to FIG. 7, a flow diagram depicts a process for managingdeactivation of game controllers at detachment from a bridge. Theprocess starts at step 118 in a connected state having first and secondgame controllers attached on opposing sides of a bridge. At step 120,detachment of a game controller wing from the bridge is detected. Theprocess continues to step 124 to transition the bridge firmware to a“deactivating” state and start a timer. At step 126, a determination ismade of whether all game controller wings are attached to the bridgeand, if so, the process continues to step 128 to proceed to activationat step 102 of FIG. 6. If both game controller wings are not connectedat step 126, the process continues to step 130 to decrement the timerand step 132 to determine if the timer has expired at zero. If the timerhas expired, the process continues to step 136 to set the state to “notconnected,” to update the database at step 138, and to end at step 140.If the timer has not expired, the process continues to step 134 todetermine if any of the bridge's game controller wings are attached toanother bridge. If not, the process returns to step 126. If a gamecontroller is determined as connected to another bridge, the processcontinues to step 136 to set the bridge to a not connected state, toupdate the database at step 138 and end at step 140.

Referring now to FIG. 8, a logical block diagram depicts a storagestructure for tracking game controllers 12 at an information handlingsystem 10 and bridge 20. Information handling system 10 includesoperating system drivers 144 and/or device specific drivers 150, 152 and154 that interact with a composite device database 156 to present acomposite device descriptor of composite controller assemblies 28 foruse by an application executing on information handling system 10, suchas a gaming application. In the example embodiment, driver support isprovided for communication with bridges 20 through USB, Bluetooth GATTand Internet Protocol. Various software and firmware structures andinteractions may be used to coordinate communication between compositecontroller assemblies 28 and information handling system 10. Forinstance, drivers may be implemented with multiple separate drivermodules or one single monolithic driver. Composite device database 156may be implemented as a file, a hive registry, an SQL database or otherformats. Data representations may include binary, text or other formats.In a monolithic driver embodiment, a virtual device can be representedto allow transport and other elements of the devices to be changedwithout remunerating the virtual device.

In operation, each bridge 20 boots at power up, determines its connectedcomponents, such as by reading identification information of attachedgame controller 12, and aggregates its identification with the connectedcomponent identifications to define a composite identity descriptor.Bridge 20 then interfaces with information handling system 10 through anavailable communication medium, such as USB, Bluetooth or IP, andregisters with information handling system 10. A monolithic driver 144or an individual driver associated with USB 150, Bluetooth 152 or IP154, interrogates the bridge 20 of the composite device 28, such asthrough vendor specific control messaging, and obtains the compositeidentifier. The driver then reads composite device database 156 to seeif the composite device 28, bridge 20 or game controllers 12 areincluded as devices previously in use at information handling system 10.If so, the driver in contact with the composite device interfaces withany companion drivers to remove the device from its connected devices.The connected driver then registers the composite device in compositedatabase 156 and stores its identity descriptor. As components are addedor removed, such as different bridges or changes to game controllers atdifferent bridges, updated identifier information is provided throughits active driver to maintain consistent tracking of bridges and gamecontrollers interfaced with information handling system 10. In oneexample embodiment, composite database 156 includes tracking of bridgesand game controllers with a “pause” state that indicates a transitionbetween connected and disconnected states, such as when a gamecontroller is detached from information handling system 10 or bridge 20to attach to a different device. In some cases, the MCU 162 oninformation handling system 10 and game controller(s) 12 directlyconnected to that MCU 162 represent the game controller(s) 12 as acomposite device to the database via USB. In such an example embodiment,MCU(H) 162 of information handling system 10 could be managed the sameway as the bridges 20 within the database, such as for exampletransitioning to different states depending on game controller 12identifier tracking. Thus, for instance, game controller interactionswith bridges and information handling systems are trackable asconnected, disconnected, paused, active, inactive and other states sothat transitions of composite devices, to include information handlingsystem and controller composite devices, are actively managed to providesmooth operating transitions, such as during re-configuration of gamecontrollers between different bridges and information handling systems.

Referring now to FIG. 9, a circuit block diagram depicts an exampleembodiment of an information handling system 10 attached at opposingsides of a housing 160 to first and second game controllers 12 fordirect communication through a wired interface. In the exampleembodiment, information handling system 10 includes processingcomponents within a housing 160 having an attachment structure asdescribed above to attach to a game controller 12 housing. The exampleembodiment depicts a microcontroller unit (MCU) 162 that interfaces withconnector pads 66 and accelerometers 170 through an I2C interface 168. AUSB interface 166 is provided to a system on chip 164 that provides USBhub and wireless communication support. Although the example embodimentdepicts an MCU, other types of processors may be used and, in an exampleembodiment, the system CPU may directly couple to the connector pad 66instead of communicating through MCU 162. Each game controller 12includes an MCU 172 that executes embedded code stored in flash memoryto monitor for input device inputs and report the inputs through pogopin connector 56 to information handling system 10. In the exampleembodiment, input devices include input buttons associated with ajoystick 14 and joystick and trigger inputs 176. Other features that maybe optionally supported include a speaker 180 that plays audio providedfrom information handling system 10 and a secondary battery supply 182that supplements information handling system integrated battery storage.These additional features may be supported, for instance, withadditional wired interface pins as described below. In addition topassing inputs to information handling system 10, each game controller12 includes a motor driver 178 that drives a haptic device to generate ahaptic response, such as a vibration, with a drive command, such aspulse width modulation (PWM) or a logical vibration response level. Inthe example embodiment a vertical linear resonant actuator (LRA) 184 anda horizontal LRA 186 provide haptic feedback or “rumble” to the end userbased upon commands communicated from information handling system 10,such as a command for vibration at variable levels in horizontal andvertical orientations. In an alternative embodiment, a single eccentricrotating motor (ERM) or dual ERMs with horizontal and verticalorientation may be used. Accelerometers 170 integrated in informationhandling system 10 and game controller 12 detects vibration andgyroscopic orientation. As described in greater detail below, the amountof haptic feedback may vary based upon the physical configuration of thegame controller, such as using a lower motor speed when in a low weightconfiguration coupled to bridge 20 and a greater motor speed when in ahigh weight configuration coupled to information handling system 10.Haptic feedback may also vary based upon the orientation of gamecontroller 12, such as by adjusting the speed of the horizontal versusthe vertical motor as orientation detected by gyroscopic function of theaccelerometers 170 changes.

Referring now to FIG. 10, a circuit block diagram depicts an exampleembodiment of a bridge 20 attached at opposing sides of a housing tofirst and second game controllers 12 for supporting indirectcommunication of the game controllers 12 with an information handlingsystem 10. Bridge 20 includes a bridge MCU 190 that supportscommunication with an information handling system through a USBinterface 166 and a wireless interface supported through a radio 192.MCU 190 interfaces through an I2C interface 168 with an integratedaccelerometer 170 and connector pad 66. Bridge 20 communicates with gamecontrollers 12 in a similar manner to information handling system 10 andacts as an intermediary with between game controllers 12 and informationhandling system 10. For example, as inputs are made at game controller12, the input are communicated through the wired interface to bridge 20and then forwarded from bridge 20 to information handling system 10through a USB cable or wireless interface. Commands from informationhandling system 10 are similarly intermediated with communications tobridge 20, which forwards the commands to game controller 12, such as toprovide haptic feedback. In the example embodiment, the identificationand ground pins are located at the bottom of the connectors and the VDDpower pin is located at the top so that inadvertent power on isprotected against and to aid the timing of power up at a slidingattachment of a controller to an information handling system or bridge.

The distributed logic architecture of FIGS. 9 and 10 provides a flexiblegame console that adapts to both handheld and standalone use cases byinterchangeably attaching game controllers to an information handlingsystem housing and a bridge housing. In the example embodiment,scalability, modularity and responsiveness of game controllers 12 areenhanced by including a processor in each game controller that managesinteractions with bridge 20 and information handling system 10.Distributed MCU processing provides a number of advantages. Oneadvantage is responsiveness of game controllers 12 and bridge 20 incommunicating game inputs to information handling system. For example,each MCU executes a state machine that rapidly responds to events, suchas inputs from a joystick, buttons and triggers and commands to hapticfeedback devices. As another example, a scalable low pin count wiredinterface simplifies communications between game controllers 12 withbridge 20 and information handling system 10. Defining a scalable lowpin count interface allows ready attachment between a bridge orinformation handling system with adaptability for optional functions andhardware interfaces. For instance, event-based state machine managementof inputs at a game controller and bridge share an I2C interface thatcan include support for other hardware through a common link. The lowpin count leaves room at the wired interface to add pins forcommunicating hardware specific information through dedicated links,such as audio information or power transfer from a battery in a gamecontroller to supplement power at an information handling system. Themodular approach of separating a composite controller assembly into abridge and two game controllers enhances reusability of each portion indifferent assemblies, reuse of common MCU embedded code and reduction ofsometimes confusing wireless interfaces by leveraging bridge wirelesscommunications. In one example embodiment, an application programminginterface defined for the wired interface supports third party vendordevices to interface with a bridge or information handling system toenhance user options for game controllers and other accessories. Tosupport adaptation to changing hardware and communication capabilities,firmware updates are coordinated across the wired and wirelessinterfaces with version control logic and malicious code protection asdescribed in greater depth below.

Referring now to FIGS. 11A, 11B and 11C, a flow diagram depicts anexample embodiment of identification by a bridge or information handlingsystem of game controller type based upon wired interface contactsduring a sliding attachment motion. Identification of pin count andconfiguration during a sliding attachment motion improves flexibilityfor integrating different types of functions within a game controllerand supporting third party game controller implementations to create arich ecosystem of compatible peripheral devices. For instance, variousconfigurations of supporting hardware integrated in a game controller,such as peripheral speakers, a supplemental battery, a camera, a smalldisplay, etc . . . . , may include additional wire interface pinconnections and/or a different order for the pins. Monitoring pin andpad interfaces of a wired connection through a sliding attachment motionsupports detection of pin connection success across plural differentgame controller hardware and pin configurations, such as third partyimplementations that may vary the pin arrangement. In one exampleembodiment, detecting pin interfaces through sliding connection processallows elimination of some pins, such as identifier pins, since the gamecontroller type is determined by the pin interfaces during theconnection process. In one embodiment, the sliding connection pininterfaces may further supplement game controller operations byproviding a power on command without a dedicated power on pin.

In the example embodiment depicted by FIG. 11, a magnet and Hall sensorare disposed in fixed positions at opposing sides of the attachmentstructure, such as with the Hall sensor interfaced with an MCU disposedin a bridge or information handling system. At step 194, the first partof a game controller 12 attachment to a bridge 20 is started withalignment of a ground pogo pin 8 with an identifier pin 1 of the bridge.For instance, at initiation of attachment, the attachment structuremisaligns both sides of the wired interface so that no pins connect withthe sliding attachment motion first bringing the game controller 12number 1 pin into contact with the bridge 20 number 8 pin. In onealternative embodiment, the number 1 pin is a dedicated identifier pinthat provides identification of the game controller device. In analternative embodiment, the number 1 pin may be repurposed afterattachment to provide support for I2C communication, thus reducing thetotal pin count. At step 194, a voltage out from the Hall sensor isprovided to an analog pin of the bridge MCU so that the variable voltageout provides an indication of the presence of the magnet and itsrelative distance to the Hall sensor. At step 196, the attachmentstructures slide from the misaligned position towards an alignmentposition with the relative voltage output by the Hall sensor reaching ahigh value half way through the sliding motion has the magnet and Hallsensor align with game controller 12 ground pin number 8 contacting thebridge number 4 pin. At step 198 as the sliding attachment motioncompletes, the voltage out from the Hall sensor decreases with themagnet moving farther away from the Hall sensor until the number 8ground pins align at opposing sides of the wired interfaces. During thesliding attachment, each pin of the bridge 20 wired interfaces brieflytouches ground to provide an additional indication of the alignment ofboth sides of the wired interface through the attachment process asdescribed in greater detail below. In particular, the example embodimentillustrates that pins 4 through 7 of game controller 12 may be initiallyconfigured as empty and then used to supplement I2C and USBcommunication once the type of game controller and its features areidentified.

Referring now to FIG. 12, a flow diagram depicts a process for detectinggame controller active pin count during a sliding attachment motion. Theprocess starts at step 200 with alignment of the attachment structuresto an initial position with the wired interfaces misaligned. At step202, the bridge processor polls analog voltage output by the Hall sensorto estimate the relative location of the wired interfaces based upon ananalog conversion of the detected voltage and sets the value L as thepin value. The wired interface relative alignment may be estimated basedupon expected voltage levels, such as with a calibration performed aftereach completed attachment where the magnet ends at the same distancefrom the Hall sensor as it has on initial misalignment. Alternatively,relative alignment may be estimated as voltage levels change through thesliding attachment motion. At step 204, a determination is made ofwhether the location determined by the Hall sensor has a value and, ifnot, the process returns to step 202 to continue polling for detectionof a pin at the location indicated by the Hall sensor. Once the Hallsensor locates a pin with the output voltage at step 204, the processcontinues to step 206 to determine whether the bridge pin number 1 isgrounded. If the bridge pin number 1 is not grounded, the processcontinues to step 208 to determine if the location is the number 1bridge pin. If the location is the number 1 bridge pin, a ground isexpected so that a failure to detect ground continues to step 210 to endthe process with an indication of a bad ground. If at step 208, thelocation is not the number one pin, the process continues to step 214 toindicate that the pin location is empty. If at step 206 the bridgenumber 1 pin is grounded, the process continues to step 212 to store thepin location L as populated. From steps 212 and 214, the processcontinues to step 216 to determine if the position L has reached theeighth and last pin. If not, the process returns to step 202 to continuewith the detection of the next pin location. Once the final pin locationis reached, the process ends at step 218.

Referring now to FIG. 13, an alternative embodiment of game controller12 pin arrangements is depicted having an identifier pin used as anindication of the number of used and empty wired interface pins. In theexample embodiment, pins 6, 7 and 8 of the bridge 20 connector 66supports an identification pin at each location with communicationbetween connector 66 and MCU 162 managed through first and secondmultiplexors 220. In the example embodiment, if pin 6 is anidentification pin, MUX 1 220 routes pin 6 to ID_H1; if pin 7 is anidentification pin, MUX 2 220 routes pin 7 to ID_H2; and if pin 8 is anidentification pin, it proceeds directly to ID_H3 at MCU 162. Pins 6 and7 alternatively configure through multiplexors 220 as a second I2Ccommunication link, although other types of alternative interfaces maybe used. Logic in MCU 162 selects multiplexor 220 routing based upon thelocation of the identification pin. For instance, at initial attachmentMCU 162 polls each of pins 6, 7 and 8 to determine which is theidentification pin and selects the multiplexors accordingly.

Referring now to FIGS. 14A and 14B, a circuit block diagram depicts aseven pin count wired interface between an information handling system10 and first and second game controllers 12 coupled at opposing sides.In the example embodiment, pin 7 is dedicated to a physical power switchcontrol 221 that aligns to a guide button functionality so that duringattachment of controller 12 to information handling system the guidepresses power switch control 221 to power up game controller 12. Duringattachment, interfacing the guide against power switch control 221 actsas a dedicated power button with a press to complete power up and downsequencing between game controller 12 and information handling system10. For example, 5V of power is provided through pin 1 to each gamecontroller 12. The identification pin 6 for both the left and right gamecontrollers 12 is grounded to only provide an attachment indication whenattachment is complete so that power is communicated from switch 220.

Referring now to FIGS. 15A and 15B, a circuit block diagram depicts asix pin count wired interface between an information handling system 10and first and second game controllers 12 having an identification pinrepurposed to control power. In the example embodiment, a power control222, such as a diode, is disposed between MCU 172 and the identificationpin assigned to pin 6 so that MCU 172 commands power up and down basedupon the high or low value of identification pin 6. When theidentification pin is pulled low at connection to information handlingsystem 10, logic on MCU 172 and information handling system 10coordinate to apply power to game controllers 12 at pin 1 with 3.3V andthe game controllers enter power up. Using the identification pin as adual purpose for both detecting attachment and commanding power up anddown eliminates the need for dedicated pin 7 and the power switch of theembodiment of FIGS. 14A and 14B. Although the example embodiments ofFIGS. 14A, 14B, 15A and 15B address attachment of game controller 12 toinformation handling system 10, a substantially identical circuit may beused with attachment of game controller 12 and bridge 20. Generally,information handling system and bridge attachments operateinterchangeability to attach to game controllers 12.

Referring now to FIG. 16, a circuit block diagram depicts an exampleembodiment having opposing pins pulled high and to ground to confirmattachment connections before game controller power up. In the exampleembodiment, game controller 12 has all pins at connector 56 pulled lowand information handling system 10 has all pins at connector 66 pulledhigh. Electrical communication between connectors 56 and 66 is confirmedonce all pins are shorted to ground. Once electrical connections areverified by short to ground, a power up sequence is initiated andapplying power at game controller 12 breaks the ground connection there.To support connection testing, test circuit 226 provides a multiplexor220 between connector 66 and MCU 162 at each pin to interface eachconnector pin 66 with both its logical pin at MCU 162 and a test pin atMCU 162. At the game controller side, a high impedance circuit 224interfaces with each pin of connector 56 to provide ground to each pin.The test VDD is applied by logic at MCU 162 so that the test pins can beread to determine ground. Once each test pin detects ground, a goodconnection of connectors 56 and 66 is determined and power up of thegame controller breaks the ground connection at high impedance circuit224. In example embodiment, Schottky diodes are disposed in highimpedance circuit 224 and p-channel FETs are disposed in test circuit228.

Referring now to FIG. 17, a flow diagram depicts a process forconfirming game controller attachment with the example embodiment ofFIG. 16. The process starts at step 228 and at step 230 the gamecontroller “wing” is connected to the information handling system orbridge. At step 232, test circuit 226 sets the multiplexors 220 to routeto the test pins of MCU 162. At step 234, the game controller highimpedance test circuit 224 defaults to interface ground to the connector56. At step 236, logic of MCU 162 turns on power to the test VDD tobring all of the pins of connector 66 to a high state. At step 238, MCU162 listens to each of the test pins to detect a high or low state. Atstep 240, MCU 162 stores a list of the high or low states at each pin ofconnector 66 at step 244. Once the test is completed, the VDD is poweredon, which breaks the connection of the pin with the test VDD, the testVDD is powered down and MCU 162 queries the game controller to retrievea list of the pins used by the game controller. At step 246, adetermination is made of whether the list is received and, if not, theprocess continues to step 250 to indicate an error. If the list isreceived, the process continues to step 248 to compare the list ofactive pins with the list of pins provided from the game controller. Ifa pin from the game controller list is not active, an error is indicatedat step 250. If all of the pins indicated as used by the game controllerare active, the process ends at step 252 with an indication of asuccessful connection.

Referring now to FIG. 18 a flow diagram depicts a process for updatingfirmware at game controllers 12, bridges 20 and information handlingsystems 10. Although interchangeability of game controllers withdifferent capabilities as attached to different bridges and informationhandling systems provides improved flexibility for end users, changingconfigurations may result in different embedded code versions operatingon the MCU within each game controller, bridge and information handlingsystem. In order to ensure consistent communications and interactions,each MCU stores locally a firmware version and communicates the firmwareversion upon attachment. For example, embedded code firmware is storedin non-transient memory of the MCU or interfaced with the MCU, such asprogrammable static random access memory (SRAM) or other flash memorydevices. If one device in an attached configuration has a more recentfirmware version than another device, the firmware update processdepicted by FIG. 18 is initiated to update the embedded code. In oneexample embodiment, each MCU in the game controller, bridge andinformation handling system executes a common version of embedded codethat supports individual device functions based upon identification ofthe device type. With the same embedded code distributed to gamecontroller, bridge and information handling system MCUs, the MCU withthe most updated embedded code copies its firmware to the other devices.In one example embodiment, a game controller with a most updatedembedded code version copies the embedded code to an informationhandling system, which in turn copies the update to a second gamecontroller attached at an opposing side of the information handlingsystem. A similar process may take place where a bridge receives afirmware update from a first game controller and provides the update toa game controller at an opposing side of the bridge.

A most likely firmware update scenario involves the information handlingsystem getting firmware updates through a network interface andcommunicating the firmware updates directly to attached gamecontrollers, directly to a bridge through a wireless or USB interface,or indirectly to game controllers that are attached to a bridge. If theinformation handling system, bridge and game controller MCUs rundifferent code, a copy of each device type firmware may be stored oneach device to support updates between devices. In some instances, olderversions of firmware may be stored at a device to execute in a situationwhere an attached device cannot perform an update. Security measures toensure that malicious code is not loaded may include a verification orsecurity code associated with an update, such as based upon a hash ofthe update.

In the example embodiment, an embedded code update is initiated from ahost information handling system device to a “wing” game controllerdevice. In alternative embodiments, as described above, firmware updatesmay be initiated from any device that has a most recent embedded codeversion. The process starts at step 254 with a request by the hostoperating system, such as WINDOWS, to initiate a game controller MCUembedded code update. The “head” information handling systemcommunicates the requested update at step 256 as a reset command toplace the game controller MCU in a bootloader mode. At step 258, afterentering the bootloader mode the game controller responds with a messageindicating that it is prepared to accept the update. The informationhandling system MCU at step 260 forwards the bootloader initiatedmessage to the host operating system. At step 262 the host operatingsystem sends 32 Byte firmware update packets to the information handlingsystem MCU, which, at step 264, forwards the firmware update packets tothe game controller MCU. Steps 262 and 264 repeat until the firmwareupdate transfer to the game controller is complete. At step 266, thehost operating system sends an update done message to the informationhandling system, which, at step 268 forwards the update done message tothe game controller MCU. At step 270, the game controller MCU computes achecksum of the firmware update and sends the checksum to theinformation handling system MCU, and at step 272 the informationhandling system MCU sends the checksum to the host. The game controllerMCU executes the firmware update and enters normal operational mode tocommunicate with the information handling system MCU through an I2Clink, which provides communication to the host through a USB link.

Referring now to FIG. 19, a flow diagram depicts a method for adaptinghaptic response at a game controller based upon the type of operationalconfiguration of the game controller. As described above, each gamecontroller 12 integrates one or more haptic devices that provides ahaptic feedback to an end user, such as eccentric rotating mass motor(ERM) that generates vibration by rotating a weight off center from arotational axis or a linear resonant actuator (LRA) that generatesvibration using magnetic fields and electrical fields. In one exampleembodiment, a first haptic device generates vibration in a first planeand a second haptic device generates vibration in a second plane, suchas perpendicular to the first plane. As described above, each gamecontroller may attach to both an information handling system housing ora bridge housing. Since the information handling system has a greatermass than the bridge, a given haptic response will vary depending uponthe weight of the device as a whole so that a haptic response at aninformation handling system will have less vibration than the sameresponse at a bridge. In an embodiment where different hardwareconfigurations exist for game controllers, bridges and informationhandling systems, the mass of each attached device will have an impacton haptic device feedback felt by an end user. To adjust for differentsystem total mass with different configurations, haptic feedback isadjusted based upon total mass and refined based upon accelerationssensed at the information handling system. For example, an accelerometerdetects actual haptic response for the game controller MCU to compareagainst intended haptic response so that the haptic device operation canbe adjusted, such as by changing the pulse width modulation applied toan ERM that generates vibration. One advantage to compensating hapticresponse based upon detected accelerations is that other factors arealso taken into account, such as the tightness of an end user grip onthe game controller, the mass of an end user's hands and situationswhere haptic response is unhelpful, such as when the game controller isresting on a table resulting in excessive vibration. In addition,orientation of the game controller sensed by the accelerometers canadjust haptic response from different haptic devices integrated out ofplane from each other, including a direction of the rotation of an ERMbetween clockwise and counterclockwise.

The process starts at step 276 and continues to step 278 to determine ifthe game controllers are attached to an information handling system,such as by retrieving device type information from the informationhandling system MCU. If the game controllers are attached to aninformation handling system, the process continues to step 280 to placethe game controller haptic device in a high weight configuration. Forinstance, a full haptic response is generated and communicated to thehaptic device to ensure that adequate vibration is felt by the end user.At step 282, the information handling system MCU passes rumble controlcommands to generate the haptic response with the full ERM motor speedto the game controller MCU. The process then continues to step 284 todetermine if accelerometers at the game controller and/or theinformation handling system detect vibration expected for the commandedhaptic response. If yes, the process returns to step 278 to continuemonitoring haptic response. If the haptic response differs from theexpected response at step 284, the process continues to step 292 tomodify the commanded haptic response to compensate for the responsedetected by the accelerations. For instance, if the haptic responsedetected by accelerometers exceeded the expected haptic response, alower ERM rotation speed is commanded; and if the haptic responsedetected by accelerometers does not meet the expected haptic response, ahigher ERM rotation speed is commanded. Similar adjustments are appliedin an LRA haptic device is used instead of an ERM haptic device.

If at step 278 the game controllers are not attached to an informationhandling system, the process continues to step 286 to determine if thegame controllers attach to a bridge, such as by exchanging a device typeidentifier with the bridge MCU. If the game controllers are connected toa bridge device, the process continues to step 288 to configure thehaptic response at a low weight configuration, such as having a reducedhaptic response in proportion to the weight of the game controllersattached to the bridge instead of the information handling system. Atstep 290, the haptic response commanded to the haptic device is reducedbased upon the reduced weight. The process then continues to step 284 tocompensate for any differences between detected accelerations andexpected accelerations of the haptic response. If at step 286 neitherthe bridge nor information handling system is attached, the processdetermines no controller and returns to step 278. At step 290, themodification of the haptic response for the reduced weightconfiguration, such as the lower ERM rotation speed, may be determinedat the information handling system and sent to the bridge or the bridgemay alter the full haptic response received from the informationhandling and provided to the game controller. In one embodiment, logicin the game controller MCU reduces the full haptic response commanded bythe information handling system or bridge to compensate at the gamecontroller for the reduced weight. As described above, the adjustmentsdetermined by monitoring sensed accelerations can include adjustments tovertical versus horizontal LRA axial vibration or ERM rotation andadjustments to the rotational direction of different ERM.

Referring now to FIG. 20, a flow diagram depicts a process of adjustinghaptic response based upon an orientation of a game controller. Invarious embodiments, the haptic response may be generated with an ERM,LRA or other types of vibration-generating devices. For instance, LRAhaptic devices tend to provide better control of the vibration axiscompared with ERM haptic devices so that a game controller withhorizontal and vertical vibration control may be implemented with twoLRA devices oriented perpendicular to each other. The process starts atstep 296 and, at step 298 a determination is made of whether the gamecontroller has a sideways orientation. Generally, while playing a gamethe game controller is expected to be within the 90 degrees of rotationdistance from the user plane. That is, the end user's expectedorientation provides a plane of expected orientation of the gamecontroller that identifies how much relative rotation should apply tofirst and second vibration response, such as LRA axial vibration oreccentric rotating masses rotating about perpendicular axes. If the gamecontroller is sideways, the process continues to step 300 to retrievefrom gyroscopic logic of the accelerometer the degree of rotation aboutthe axis of gravity. If the game controller is not sideways at step 298,the process continues to step 302 to detect the rotational degree of thegame controller relative to the ground plane. These determinations ofrelative orientation provide an X value to input to the modulusequations of step 304 that define a vibration response of avertically-orientated and horizontally oriented haptic device. Theprocess then returns to step 296 to continue monitoring game controllerorientation and adjusting vertical and horizontal vibration response. Inone example embodiment, haptic response is programmable by an end userinterface so that the end user can adapt haptic response as desired fora specific controller or gaming application, such as changes to theintensity of haptic response and changes to directional impulses.

Referring now to FIG. 21, an exploded view of a game controller 12depicts a vertical axis trigger assembly to accept end user triggerinputs. Since game controller 12 couples both directly to an informationhandling system housing and to a bridge that supports peripheraloperation, game controller 12 input devices adapt to both types ofconfigurations with a vertically aligned trigger motion. In particular,when game controllers 12 attach at opposing ends of an informationhandling system housing, the end user grasp supports not just actuationof input devices but also hand held viewing of a display integrated inthe information handling system tablet form factor. A vertically alignedtrigger motion aids end user grasp at the periphery of the informationhandling system housing while disposing actuation structure in planewith the tablet planar housing form factor, thus minimizing the impactof the input devices on system portability when game controllers 12 areattached. A difficulty with this arrangement is that index and middlefingers that typically interact with a trigger can exert a substantialforce on a trigger input device. To withstand this force and provide arobust input device with repeatable and nonbinding inputs, a triggersubassembly with vertically aligned input rotation provides idealtrigger tactile feedback and response time for trigger inputs in acomfortable end user grasp.

In the example embodiment, a trigger 310 couples as a subassembly to amidframe assembly 308 to provide robust trigger inputs independent of acosmetic outer housing. Coupling the trigger 310 as a subassemblyprovides isolation and independent actuation for trigger movement andreduces complications associated with manufacture and assembly of thegame controller. Trigger 310 pivots about a vertical rotational axisrelative to the plane of a grasped information handling system housingthat aligns with an input fingers natural motion. In the exampleembodiment, a midframe 308 provides the main structural integrity of thegame controller with attachment structure 50 defined at a side surfaceto attach to an information handling system housing. For instance,attachment structure 50 at the side surface of midframe 308 definesslots with an enhanced material thickness for a robust informationhandling system attachment in combination with lips that overlap theside surface when a cosmetic housing couples over midframe 308. Anopening in the side surface of attachment structure 50 provides spacefor a wired connector, such as pogo pins 56, disposed at a printedcircuit board 306 to insert through and interface with an informationhandling system wired interface. Printed circuit board 306 couples to anupper surface of midframe 308 with screws 314 to provide communicationbetween the input devices, MCU and pogo pin connector 56. A triggerinput button 316 located at one end of printed circuit board 306 todetect inputs at trigger 310. In the example embodiment, a secondarybutton 312 is provided above trigger 310 to accept press inputs detectedby an upper portion of trigger input button 316. Input button 314provides a press input device separate from trigger 310, although inalternative embodiments input button 314 may have a vertically alignedrotation similar to trigger 310 to provide a double trigger inputdevice.

In the example embodiment, trigger 310 couples to midframe 308 to rotateabout a vertical axis defined by a dowel pin axle 334 extending up frommidframe 308 and coupling to a bracket in trigger 310 subassembly, asdescribed in greater detail below. In addition, trigger 310 motion isdefined by a member 318 that fits in a guide 320 integrated in midframe308. Rotation about axle 334 provides a rotation axis at an outerperimeter of midframe 308 relative to the position of attachmentstructure 50 so that a finger extending from an end user grasp at theouter perimeter activates trigger 310 about a natural rotation axis. Forinstance, an end user grasp around the perimeter of an informationhandling system having a game controller attached places trigger 310 inposition for a finger to activate at a front outer edge of the completeassembly.

Referring now to FIG. 22, an exploded view depicts game controllercovers 322 and 326 aligned to assemble to midframe 308. In the exampleembodiment, midframe 308 has a completed assembly with joystick 14coupled to printed circuit board 306, buttons 16 coupled to printedcircuit board 306, button 312 coupled to midframe 308 and trigger 310coupled to midframe 308. Upper housing 322 encloses the upper surface ofmidframe 308 and lower housing 326 encloses the lower surface ofmidframe 308 with an end cap 324 securing upper housing 322 to lowerhousing 326 with screws 314. A bezel 328 couples to upper housing 322and lower housing 326 to encircle trigger 310 and button 312. As isillustrated by the uncovered midframe, trigger 310 couples to midframe308 independent of upper housing 322 and lower housing 326 so thatoperation of trigger 310 does not rely upon support of the decorativeouter coating of game controller 12. The separated construction providesa more robust trigger 310 in the face of large end user input forces.

Referring now to FIG. 23, an exploded view depicts a trigger subassemblythat couples to a game controller midframe. A trigger bracket 330couples directly to midframe 308, such as with screws. Dowel pin axle334 inserts through vertically aligned openings of trigger bracket 330and through openings 338 formed at the rotational axis location oftrigger 310. A torsion spring 332 fits over dowell pin axle 334 tocreate a biasing force that biases trigger 310 away from midframe 308.During manufacture, trigger bracket 330 is assembled to have trigger 310coupled by dowel pin axle 334 with spring 332 engaged so that thesubassembly is then coupled to midframe 308, thus reducing assembly timeand complexity. Guide member 336 fits into a guide formed at midframe308 to further simplify assembly and guide trigger 310 motion duringtrigger inputs.

Referring now to FIG. 24, a lower perspective view depicts trigger 310actuation at a midframe 308. FIG. 25 depicts trigger 310 actuation froma bottom view. Trigger 310 rotates about a vertical axis towardsmidframe 308 without relying upon any outer cosmetic cover as support.An elastomeric end stop dampener integrates with midframe 308 at a stoppoint for trigger 310 rotation to absorb the force of an end usertrigger input. A gap 342 formed in midframe 308 at the periphery oftrigger motion aids in guiding trigger 310 towards dampener 340. Button312 actuates separate from trigger 310 and also supported by midframe308 without relying upon the outer housing.

Referring now to FIG. 26, a lower front perspective view of midframe 308illustrates guide structures disposed to aid in trigger motion. In theexample embodiment, elastomeric dampener 340 integrates with midframe308 structure to provide a firm stop for trigger motion with forcepartially absorbed at the stop by elastomeric material, such as anelastomeric plastic. A trigger guide tab 336 extends out from a midframeguide rail 320 to engage with the trigger and guide trigger motion. Abutton guide tab 344 extends out from midframe guide rail 320 to guidebutton motion at a press towards midframe 308.

Referring now to FIGS. 27A and 27B, a lower perspective exploded viewdepicts an illumination assembly that provides illumination at ajoystick 14 extending from an upper surface of game controller 12.Illumination of different colors and intensities at game controller 12provide indications to an end user about both the operational status ofthe game controller and gaming application status communicated from agaming application executing on an information handling system, eitherthrough a direct wired interface or through indirect bridgecommunications. In the example embodiment, lighting effects are providedin a controlled and focused manner by directing illumination of adesired color and intensity at a circumference defined around the baseof joystick 14. In some local operational instances, an MCU of gamecontroller 12 locally determines the illumination for presentation. Forinstance, during a power up boot, a local game controller MCU mightflash a first color and, after communication is configured for a coupledbridge or information handling system, the local MCU might flash anothercolor as a success indication before handing control of illumination tothe bridge or information handling system. Other types of locallydetermined illumination by the game controller MCU may include a failureto communicate with a bridge or information handling system, amismatched firmware or hardware version. In some instances, illuminationcontrol is determined at bridge to present operational status asdetermined by the bridge, such as a lack by the bridge of acommunication interface with an information handling system through USB,Bluetooth or IP communications. In addition, these operational statusindications may be commanded from an information handling system to theillumination assembly where operational status issues are determined atthe information handling system. In an operational mode, illuminationcolor and intensity is supported by the operating system so that gamingapplications can include indications that might include gaming events,such as loss of life, life status, alerts, etc . . . .

To direct illumination to a defined region at joystick 14, a pluralityof red, green and blue (RGB) LEDs 356 are powered through a flexibleprinted circuit board strip that is mounted in a circular fashion arounda translucent plastic light guide, such as may be formed with a doubleshot injection molding process. The top housing light guide 322 has atranslucent region proximate joystick 14 and formed as an innercircumference at the opening through which joystick 14 extends. Anon-translucent region 354 is defined around the outer circumference ofthe translucent region to form a boundary at which illumination iscontained. A light guide 360 integrated in housing 322, such as with adouble shot plastic injection of a translucent plastic, forms anenclosure that surrounds joystick 14 and defines a pathway through whichillumination proceeds from the interior of game controller 12 totranslucent region 352. An LED gasket 350 couples around the base oflight guide 360 to have openings through which LEDs 356 of light ringflexible printed circuit 348 fit to transmit light into light guide 360.LED light gasket 350 seal illumination to proceed into light guide 360without leaks into the game controller main body that might distract anend user. In one embodiment, non-translucent region 354 and region 358is treated to prevent transmission of light, such as with a layer ofpaint or other covering. In another embodiment, light guide 360 isformed as a separate piece that assembles into game controller 12 withlight gasket 350 and light right flexible printed circuit board coupledinto place. Light ring flexible printed circuit board has a tail thatcouples to the game controller main printed circuit board to acceptcommands from the game controller MCU that defines illumination colorand intensity.

Referring now to FIG. 28, an upper perspective view depicts a controllerhousing conical light guide portion. The light guide 360 acceptsillumination from a side surface about its circumference to allow spacefor a generous array of LEDs for good variations in LED color andintensity. Inner portions of light guide 360 may be treated to directlight towards the circular opening through which the joystick fits andto prevent illumination leakage where such leakage could distract an enduser. A mount clearance area 358 fits over portions of the joystick andaids in alignment at assembly. FIG. 29 depicts a side perspective viewof flexible printed circuit 348 having LEDs 356 to illuminate ajoystick. A mount clearance 358 aligns with that of light guide 360 toaid in assembly and coupling of the flexible printed circuit board tothe main game controller printed circuit board.

Referring now to FIG. 30, a side cutaway view depicts a joystick 14illuminated by five LEDs 356 mounted at a bottom location. LEDs 356 tendto have difficulty directing illumination from the bottom locationtowards joystick 14 due to the interference area of the encasementaround joystick 14 and the optical lens provided to a light guide thatdirects the illumination toward the game controller upper surface. FIG.30B illustrates non-uniformity that is provided by the bottomillumination at a translucent region 352. FIG. 30C illustrates reducedillumination levels achieved at the joystick 14 circumferencetranslucent region 352.

Referring now to FIG. 31, a side cutaway view depicts a joystick 14illuminated by ten LEDs 356 mounted at a side location. The greatersurface area of light guide 360 around its circumference provides spaceto arrange LEDs 356 to direct illumination in an efficient and effectivemanner towards translucent region 352. As a result, illuminationuniformity depicted by FIG. 31B is improved relative to bottomillumination and a greater illumination intensity is available asdepicted by FIG. 31C.

Although the present invention has been described in detail, it shouldbe understood that various changes, substitutions and alterations can bemade hereto without departing from the spirit and scope of the inventionas defined by the appended claims.

What is claimed is:
 1. An information handling system comprising: a mainhousing; a main processor disposed in the main housing and operable toexecute instructions that process information; a memory disposed in themain housing and interfaced with the main processor, the memory operableto store the instructions and information; a main wired link interfacedwith the main processor and exposed at the main housing at a main portto communicate information through plural main pins; a controllerhousing configured to selectively couple and decouple with the mainhousing; a controller processor disposed in the controller housing andoperable to execute instructions that process information and to acceptinputs at an input device integrated with the controller housing; acontroller wired link interfaced with the controller processor andexposed at the controller housing at a controller port to communicationinformation through controller pins, the controller port, duringcoupling of the controller housing to the main housing, sliding relativeto the main port from an unaligned position to an aligned position, thealigned position having the controller pins aligned with the main pins;and a non-transitory memory interfaced with the main processor andstoring instructions that execute on the main processor to analyzecontroller pin and main pin alignments during the sliding of thecontroller port and main port to identify at the main processor a typeof controller.
 2. The information handling system of claim 1 furthercomprising: a bridge housing; a bridge processor disposed in the bridgehousing and operable to execute instructions that process information; abridge wired link interfaced with the bridge processor and exposed atthe bridge housing at a bridge port to communicate information throughplural bridge pins; wherein the controller port, during coupling of thecontroller housing to the bridge housing, slides relative to the bridgeport from the unaligned position to the aligned position, the alignedposition having the controller pins aligned with the bridge pins; anon-transitory memory interfaced with the bridge processor and storinginstructions that execute on the bridge processor to analyze controllerpin and bridge pin alignments during the sliding of the controller portand bridge port to identify at the bridge processor the type ofcontroller.
 3. The information handling system of claim 2 wherein thetype of controller comprises a gaming controller type having a joystickand trigger integrated in the controller housing and interfaced with themain processor at alignment of the main and controller ports.
 4. Theinformation handling system of claim 2 wherein the type of controllercomprises a speaker controller type having a speaker integrated in thecontroller housing and interfaced with the main processor at alignmentof the main and controller ports.
 5. The information handling system ofclaim 2 wherein the type of controller comprises a battery controllertype having a battery integrated in the controller housing andinterfaced with the main processor at alignment of the main andcontroller ports.
 6. The information handling system of claim 1 furthercomprising: a magnet integrated in the controller housing; and a Hallsensor integrated in the main housing, the magnet and Hall sensor havinga first alignment at initiation of coupling of the controller housingand main housing and a second alignment at completion of sliding of thecontroller port and main port to the aligned position.
 7. Theinformation handling system of claim 6 wherein a ground pin of thecontroller pins interfaces with a predetermined of the bridge pinsduring the sliding of the bridge port relative to the controller port,the bridge processor identifying the type of controller based upon thealignment of the ground pin relative to the position of the Hall sensorand magnet.
 8. The information handling system of claim 1 furthercomprising: first and second multiplexors disposed between the main portand the main processor, each multiplexor accepting a communicationsignal from one pin of the main port and providing the communicationsignal to a first or second pin of the main processor; wherein the mainprocessor commands the first and second multiplexors to direct thecommunication signal to the first or second pin based upon one or morepredetermined factors.
 9. The information handling system of claim 8wherein the one or more predetermined factors include alignment of anidentifier pin of the controller port with a predetermined pin of themain port.
 10. A method for interfacing a peripheral device with aninformation handling system, the method comprising: detecting duringsliding of the peripheral device and information handling systemrelative to each other a contact of a peripheral device interface pinwith plural information handling system interface pins; detecting thesliding aligns plural peripheral device interface pins with associatedof the plural information handling system interface pins; and analyzingat the information handling system signals associated with thecontacting during the sliding to identify the peripheral device at theinformation handling system.
 11. The method of claim 10 furthercomprising: coupling a magnet to the peripheral device proximate theplural peripheral device pins; coupling a Hall sensor to the informationhandling system proximate the information handling system interfacepins; and comparing Hall sensor indications and information handlingsystem signals associated with the contacting during sliding to identifythe peripheral device.
 12. The method of claim 11 wherein: the analyzingcomprises detecting a ground interface pin of the peripheral deviceagainst a predetermined of the information handling system pin; and thecomparing Hall sensor indications comprises determining a distancebetween the Hall sensor and magnet at the detecting the ground interfacepin.
 13. The method of claim 10 further comprising commanding one ormore multiplexors based upon the analyzing to adjust communication ofsignals from the peripheral device through the information handlingsystem interface pins to selected pins of a processor of the informationhandling system.
 14. The method of claim 10 further comprising: pullingall peripheral device interface pins to a low state; pulling allinformation handling system interface pins to a high state; andverifying completion of the sliding when all information handling systeminterface pins are pulled to a low state.
 15. The method of claim 14further comprising: detecting one of the information handling systeminterface pins remaining at a high state; and re-assigning a function ofthe one of the information handling system interface pins to another ofthe information handling system interface pins.
 16. The method of claim15 wherein the identifying the peripheral device further comprisesidentifying a type of functional addition to a game controller.
 17. Agame controller comprising: a bridge processor coupled to first andsecond bridge wired interfaces, the first and second wired interfacesaligned to couple with the first and second controller wired interfacesto communicate information between the bridge processor and first andsecond controllers; non-transient memory interfaced with the bridgeprocessor and storing instructions that when executed on the bridgeprocessor detects signals at the bridge wired interface from contactwith each of the first and second controller wired interfaces as thebridge slides relative to each of the first and second controller wiredinterfaces, the signals applied to identify at the bridge processor atype of controller associated with each of the first and secondcontroller wired interfaces.
 18. The game controller of claim 17 whereinthe first controller wired interface comprises speaker interfacescoupled to a speaker that plays audio, the first controller wiredinterface supporting a communication medium for communicating audioinformation.
 19. The game controller of claim 17 wherein the signalcomprises a ground pin of each of the first and second controller wiredinterfaces contacting the bridge wired interface in a predeterminedsequence.
 20. The game controller of claim 19 further comprising: amagnet disposed proximate the second controller wired interface; and aHall sensor disposed in the bridge housing and interfaced with thebridge processor to provide a signal of the distance of the Hall sensorfrom the magnet, the instructions applying the distance and the groundpin interface to determine the type of the controller.